-
Notifications
You must be signed in to change notification settings - Fork 324
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump Consul version to 1.10.2 #718
Conversation
1e15bc7
to
90695aa
Compare
The world needs this PR @lkysow 😄 👍 in this PR even in draft. |
If the mesh gateway tests fail, the acceptance tests will now write two files <PODNAME>-envoy-configdump.json and <PODNAME>envoy-clusters.json which will have information from the envoy admin /config_dump endpoint and /clusters endpoint. Currently we write the outputs of `kubectl logs POD` and `kubectl describe POD` for the acceptance tests, but while debugging EKS acceptance test failures, it was hard to know from our existing logs whether the mesh gateway itself is unreachable or if the consul servers behind it are unhealthy. We'd be able to tell this from looking at the envoy config dump and cluster config to see what envoy's view of the consul servers are.
00afd55
to
69a166b
Compare
- fix tests that were failing due to a change in how the DestinationUpstream field is set in Consul OSS vs Enterprise. - set use_streaming_backend to false for Consul clients because streaming is not currently supported with mesh gateway federation
69a166b
to
4035e6e
Compare
@@ -24,7 +24,8 @@ data: | |||
in the UI. */}} | |||
config.json: |- | |||
{ | |||
"check_update_interval": "0s" | |||
"check_update_interval": "0s", | |||
"use_streaming_backend": false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I put this here because it only causes issues when doing federation and consul connect
@@ -543,7 +543,7 @@ load _helpers | |||
#-------------------------------------------------------------------- | |||
# config-configmap | |||
|
|||
@test "client/DaemonSet: adds config-checksum annotation when extraConfig is blank" { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just re-worded the test titles a bit here because it always adds the config-checksum annotation so really what we're testing is that the checksum changes when the configmap is different
- fix tests that were failing due to a change in how the DestinationUpstream field is set in Consul OSS vs Enterprise. - set use_streaming_backend to false for Consul clients because streaming is not currently supported with mesh gateway federation
DestinationUpstream field is set in Consul OSS vs Enterprise.
streaming is not currently supported with mesh gateway federation
How I've tested this PR:
How I expect reviewers to test this PR:
Checklist: